chore: untrack .maestro/ Auto Run history#36
Conversation
Maestro writes per-machine Auto Run history to .maestro/history/*.jsonl; these are local artifacts and should never have been committed. Add .maestro/ to .gitignore and untrack the existing .maestro/history/history-nuc-ii.jsonl. Working copies are preserved. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Brings in installer bugfixes (PRs #33-#35), .maestro/ untrack (#36), and the docs split (#37) that landed on main after rc was branched. Conflict resolutions: - Kept rc's queue error-hiding (PR #39) and per-message logger.error. - Kept rc's WAL-checkpoint shutdown alongside main's split DB import. - Combined main's docs split with rc's Slack provider additions in README.md, AGENTS.md, .env.example, install.sh, providers.ts, migrations.ts. - Extended config_complete in maestro-relay-ctl.sh to cover the Slack key set when ENABLED_PROVIDERS=slack.
1 participant
Summary
`.maestro/history/*.jsonl` is per-machine state Maestro writes during Auto Run, not source. The current repo has `.maestro/history/history-nuc-ii.jsonl` committed (8 lines from a `feat/feat-cli` worktree run on @chr1syy's `nuc-ii` machine), which should never have been pushed.
No code changes; no version bump (this directory was never included in the release tarball anyway — the workflow only ships `dist`, `bin`, `templates`, `package*.json`, `.env.example`, `README.md`, `LICENSE`).
Test plan
🤖 Generated with Claude Code